Process model identification in a process control system

ABSTRACT

Disclosed is a method of controlling and managing a process control system having a plurality of control loops. The method includes implementing a plurality of control routines to control operation of the plurality of control loops, respectively. The plurality of control routines may include at least one non-adaptive control routine. Operating condition data is then collected in connection with the operation of each control loop of the plurality of control loops, and a respective process model is identified for each control loop of the plurality of control loops from the respective operating condition data collected for each control loop of the plurality of control loops. In some embodiments, the identification of the respective process models may be automatic as a result of a detected process change or be on-demand as a result of an injected parameter change.

TECHNICAL FIELD

The present invention relates generally to process control systems and,more particularly, to the identification and application of processmodels in process control systems.

DESCRIPTION OF THE RELATED ART

Process control systems, such as distributed or scalable process controlsystems like those used in chemical, petroleum or other processes,typically include one or more process controllers communicativelycoupled to each other, to at least one host or operator workstation andto one or more field devices via analog, digital or combinedanalog/digital buses. The field devices, which may be, for example,valves, valve positioners, switches and transmitters (e.g., temperature,pressure and flow rate sensors), perform functions within the processsuch as opening or closing valves and measuring process parameters. Theprocess controller receives signals indicative of process measurementsmade by the field devices and/or other of information pertaining to thefield devices, and uses this information to implement a control routineand then generates control signals which are sent over the buses to thefield devices to control the operation of the process. Information fromthe field devices and the controller is typically made available to oneor more applications executed by the operator workstation to enable anoperator to perform any desired function with respect to the process,such as viewing the current state of the process, modifying theoperation of the process, etc.

Some process control systems, such as the DeltaV® system sold by FisherRosemount Systems, Inc., headquartered in Austin, Tex., use functionblocks or groups of function blocks referred to as modules located inthe controller or in different field devices to perform controloperations. In these cases, the controller or other device is capable ofincluding and executing one or more function blocks or modules, each ofwhich receives inputs from and/or provides outputs to other functionblocks (either within the same device or within different devices), andperforms some process operation, such as measuring or detecting aprocess parameter, controlling a device, or performing a controloperation, such as the implementation of aproportional-derivative-integral (PID) control routine. The differentfunction blocks and modules within a process control system aregenerally configured to communicate with each other (e.g., over a bus)to form one or more process control loops.

Process controllers are typically programmed to execute a differentalgorithm, sub-routine or control loop (which are all control routines)for each of a number of different loops defined for, or contained withina process, such as flow control loops, temperature control loops,pressure control loops, etc. Generally speaking, each such control loopincludes one or more input blocks, such as an analog input (AI) functionblock, a single-output control block, such as aproportional-integral-derivative (PID) or a fuzzy logic control functionblock, and an output block, such as an analog output (AO) functionblock.

Control routines, and the function blocks that implement such routines,have been configured in accordance with a number of control techniques,including PID control, fuzzy logic control, and model-based techniquessuch as a Smith Predictor or Model Predictive control (MPC). Inmodel-based control techniques, the parameters used in the routines todetermine the closed loop control response are based on the dynamicprocess response to changes in the manipulated or measured disturbancesserving as inputs to the process. A representation of this response ofthe process to changes in process inputs may be characterized as aprocess model. For instance, a first-order parameterized process modelmay specify values for the gain, dead time, and time constant of theprocess.

One model-based technique, model predictive control (MPC), involves anumber of step or impulse response models designed to capture thedynamic relationships between process inputs and outputs. With MPCtechniques, the process model is directly used to generate thecontroller. When used in connection with processes that experience largechanges in process dead time, process delay, etc., the MPC controllermust be automatically regenerated using the models to match the currentprocess condition. In such cases, a process model was accordinglyidentified at each of a number of operating conditions. The introductionof multiple process models and the requisite automatic generation of thecontroller to matching the current process condition undesirablyincreased the complexity of the process control system.

Process models have also been used to set tuning parameters of PID andother control schemes using adaptive control techniques, where thetuning of the PID (or other) controller is generally updated as a resultof changes in the process model and a user-selected tuning rule. See,e.g., U.S. Pat. Publication No. 2003/0195641 entitled “State BasedAdaptive Feedback Feedforward PID Controller” and U.S. Pat. No.6,577,908 entitled “Adaptive Feedback/Feedforward PID Controller,” theentire disclosures of which are hereby expressly incorporated byreference herein.

Despite the promise of improved control performance, the use of adaptivecontrol techniques in the process industries has been limited, insofaras the techniques have often been difficult to implement in practice. Asa practical matter, model identification has typically been part of aspecial function block designed specifically for adaptive control.Unfortunately,.it is often difficult to determine which process controlloops would benefit from the implementation of adaptive control, i.e.,which loops should be selected for adaptive control capability. Onereason involves the sheer number (e.g., hundreds) of control loops andinstruments (e.g., thousands) that are monitored in a typical plant. Butregardless of the size or complexity of the plant, conventional processcontrol systems typically do not support the creation of process modelsfor all of the control loops in the plant. Making matters worse, themanual testing necessary to identify new process models for all thecontrol loops may not be practicably performed. For instance, thetesting may require the application of one or more process perturbationsthat are incompatible with an on-line process.

In operation, the adaptive control techniques have provided limiteddiagnostic capabilities. More specifically, when the adaptive controlschemes are selectively put into practice in process control, theidentified process response is generally only used to establish thetuning of the control loop. As a result, the process control system mayfail to provide an indication of an abnormal condition in the process orinstrumentation that is causing control performance to suffer.

SUMMARY OF THE DISCLOSURE

In accordance with one aspect of the disclosure, a method is useful forcontrolling a process control system having a plurality of controlloops. The method includes implementing a plurality of control routinesto control operation of the plurality-of control loops, respectively,the plurality of control routines including at least one non-adaptivecontrol routine, collecting operating condition data in connection withthe operation of each control loop of the plurality of control loops,and identifying a respective process model for each control loop of theplurality of control loops from the respective operating condition datacollected for each control loop of the plurality of control loops.

In some cases, the method further includes storing data indicative ofthe respective identified process models in a respective process modelhistory for each control loop of the plurality of control loops. Themethod may also include examining the operating condition data to detecta change therein, and triggering the process model identification whenthe change is detected.

In some embodiments, the identification may be performed in response toa user command to calculate the process model based on the collectedoperating condition data. The collected operating condition data maythen be indicative of a response to an injected parameter change appliedas a result of the user command.

The operating condition data may be indicative of on-line operation of aprocess controlled via the operation of the plurality of control loops.

The method may further include monitoring the respective process modelsidentified for each control loop to evaluate control loop performance.Alternatively or in addition, the method may also include analyzing therespective process models identified for each control loop to determinewhich control loops should utilize an adaptive control scheme.Alternatively or in addition, the method may still further includeanalyzing the respective process models identified for each control loopto diagnose control problems.

In accordance with another aspect of the disclosure, a method ofcontrolling a process control system having a plurality of controlroutines includes collecting operating condition data duringimplementation of the plurality of control routines, detecting an eventindicative of a process change in connection with a control routine ofthe plurality of control routines associated with the process change,identifying a process model for the control routine associated with theprocess change, and storing data indicative of the generated processmodel in developing a process model history for the control routineassociated with the process change.

In some cases, the method further includes automatically collecting datafor the identifying step upon detection of the event.

The method may also include identifying respective process models foreach control routine of the plurality of control routines. The pluralityof control routines may include a control routine that implements anon-adaptive control scheme.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosure, reference should bemade to the following detailed description and accompanying drawingfigures, in which like reference numerals identify like elements in thefigures, and in which:

FIG. 1 is a schematic representation of a process control systemincluding a controller configured with one or more control routines inaccordance with one aspect of the disclosure;

FIG. 2 is a schematic representation of the controller of FIG. 1 inaccordance with an embodiment having a model identification routine incommunication with a number of function blocks;

FIG. 3 is a schematic representation of the controller of FIG. 1 inaccordance with an embodiment in which the controller is incommunication with a workstation for model identification using trendingor other historical data;

FIG. 4 is a schematic representation of an adaptive control functionblock of the controller of FIG. 1 in accordance with an embodiment inwhich the adaptive control function block modifies tuning in accordancewith stored models and operational state information;

FIG. 5 is a schematic representation of an adaptive MPC function blockof the controller of FIG. 1 in accordance with an embodiment in whichthe MPC function block implements on-demand testing for modelidentification;

FIG. 6 is a schematic representation of the controller of FIG. 1 inaccordance with an embodiment in which identified models are stored in adatabase in association with historical event information;

FIG. 7 is a schematic representation of an alternative embodiment of theprocess control system of FIG. 1 in which a workstation implements amodel identification routine in communication with a controller via anOPC or other interface;

FIG. 8 is a schematic representation of one embodiment of the processcontrol system of FIG. 1 in which a workstation implements an exemplarysuite of applications that together provide a control performancemonitoring and management environment with associated functionality for,inter alia, loop and model analysis, diagnostics, tuning and MPC andadaptive control;

FIG. 9 is a simplified representation of an exemplary display interfacegenerated by an embodiment of the workstation of FIG. 8 having aperformance monitoring application to provide control performanceoverview information;

FIG. 10 is a simplified representation of an exemplary display interfacegenerated by an embodiment of the workstation of FIG. 8 having aperformance monitoring application to provide control loop performanceinformation for a selected system, area or other group of control loops;

FIG. 11 is a simplified representation of an exemplary display interfacegenerated by an embodiment of the workstation of FIG. 8 having aperformance monitoring application to provide performance informationfor a selected control loop;

FIG. 12 is a simplified representation of an exemplary display interfacegenerated by an embodiment of the workstation of FIG. 8 having adiagnostics or other analysis application to monitor and manage controlloop performance, adaptive model quality, and other diagnosticparameters related to a control loop;

FIG. 13 is a simplified representation of an exemplary display interfacegenerated by an embodiment of the workstation of FIG. 8 having anapplication to configure, customize and manage the model identificationprocedure for a control loop;

FIG. 14 is a simplified representation of an exemplary display interfacegenerated by an embodiment of the workstation of FIG. 8 to visualizeprocess models identified for different operating conditions indicatedby a state parameter input; and,

FIGS. 15 and 16 are simplified representations of respective exemplarydisplay interfaces generated by an embodiment of the workstation of FIG.8 having a tuning application to support and manage the use of processmodels to tune control function blocks implementing, for instance, fuzzylogic or MPC control schemes.

While the disclosed system and method are susceptible of embodiments invarious forms, there are illustrated in the drawing (and will hereafterbe described) specific embodiments of the invention, with theunderstanding that the disclosure is intended to be illustrative, and isnot intended to limit the invention to the specific embodimentsdescribed and illustrated herein.

DESCRIPTION OF PREFERRED EMBODIMENTS

Disclosed herein are a process control system and method that implementa technique that automatically identifies process models for controlloops in the process control system that are not necessarily currentlyutilizing a process model for adaptive control. The process models arecreated, therefore, for reasons other than (or in addition to) theimplementation of adaptive control. For instance, the decision as towhich control loops should have adaptive control applied thereto is madeeasier via evaluation of the process models identified via the disclosedtechnique.

In some cases, the identification of process models is extended to allcontrol loops in the process control system. In this way, process modelsmay be generated for every node of the process control system. Butregardless of whether process models are being identified for everycontrol loop or node in specific embodiments of the disclosed system,the extension of process model identification to non-adaptive controlloops has a number of benefits, including, among others, on-demandcontroller tuning, abnormal condition monitoring and diagnostics.

In some cases, process control data is collected to identify a number ofprocess models for a control loop, thereby generating a history ofprocess models. The process control data giving rise to the processmodel history may be generated during, in connection with, and as aresult of, the day-to-day operation of the process. In these cases, theresulting process model history provides a representation of the recent,on-line performance of the control loop. Special testing or testprocedures are then not required.

Where the control loop is implementing an adaptive control scheme (e.g.,an adaptive PID control), then the process model history may indicatewhether adaptive control is appropriate for the current operatingconditions or, more generally, for the control loop itself. Conversely,the process model history for a non-adaptive control loop may alsoindicate that an adaptive control scheme may be beneficial.

In some cases, the process models may be identified (e.g., generated) bya routine embedded in the process controller implementing the controlroutines. To this end, the controller may be triggered by processchanges to store process control data to support the generation of theprocess model(s). Process changes or other events that act as triggersmay include a set point change, a perturbation automatically injected inthe controller output, or any other change to the open or closed controlloop. In these and other ways, a process model identification routinemay be continuously implemented by the controller (or other element(s)of the system) to capture the process control data throughout day-to-dayoperation. Furthermore, the process models may thus be identifiedautomatically upon the detection of the process change (or other triggerevent), with all of the calculations occurring in the background whilethe process remains on-line.

Once identified and/or stored, the process model(s) may be analyzed,processed, applied or otherwise utilized to support a number of processcontrol tasks implemented in connection with managing the processcontrol system, including performance monitoring, on-demand tuning,control algorithm recommendations, loop response simulation, processmonitoring, control diagnostics, and adaptive control. For example, andas described below, the process models may be used to calculate amodel-based performance index for the control loop for which it wasidentified.

While the process models identified via the disclosed technique may alsobe relied upon to implement model-based control schemes (e.g., adaptivecontrol), implementation of the disclosed technique is not limited toany particular type of control loop, process controller, process controlsystem or process control network architecture. Moreover, the disclosedtechnique may be implemented by a number of elements of the processcontrol system, either individually or in distributed fashion, and onone or more levels (e.g., the process controller level, control looplevel, etc.). Still further, the disclosed technique is not limited toany particular process model type and, for example, may utilize anyparameterized dynamic model of the process.

Referring now to FIG. 1, a process control system 10 includes a processcontroller 11 connected to a data historian 12 and to one or more hostworkstations or computers 13 (which may be any type of personalcomputers, workstations, etc.), each having a display screen 14. Thecontroller 11 is also connected to field devices 15-22 via input/output(I/O) cards 26 and 28. The data historian 12 may be any desired type ofdata collection unit having any desired type of memory and any desiredor known software, hardware or firmware for storing data. The datahistorian 12 may be separate from (as illustrated in FIG. 1) or a partof one of the workstations 13. The controller 11, which may be, by wayof example, the DeltaV controller sold by Fisher-Rosemount Systems,Inc., is communicatively connected to the host computers 13 and to thedata historian 12 via, for example, an ethernet connection or any otherdesired communication network. The controller 11 is also communicativelyconnected to the field devices 15-22 using any desired hardware andsoftware associated with, for example, standard 4-20 ma devices and/orany smart communication protocol such as the FOUNDATION Fieldbusprotocol, the HART protocol, etc.

The field devices 15-22 may be any types of devices, such as sensors,valves, transmitters, positioners, etc., while the I/O cards 26 and 28may be any types of I/O devices conforming to any desired communicationor controller protocol. In the embodiment illustrated in FIG. 1, thefield devices 15-18 are standard 4-20 ma devices that communicate overanalog lines to the I/O card 26 while the field devices 19-22 are smartdevices, such as Fieldbus field devices, that communicate over a digitalbus to the I/O card 28 using Fieldbus protocol communications. Ofcourse, the field devices 15-22 could conform to any other desiredstandard(s) or protocols, including any standards or protocols developedin the future.

The controller 11 includes a processor 23 that implements or overseesone or more process control routines (stored in a memory 24), which mayinclude control loops, stored therein or otherwise associated therewithand communicates with the devices 15-22, the host computers 13 and thedata historian 12 to control a process in any desired manner. It shouldbe noted that any control routines or modules described herein may haveparts thereof implemented or executed by different controllers or otherdevices if so desired. Likewise, the control routines or modulesdescribed herein to be implemented within the process control system 10may take any form, including software, firmware, hardware, etc. For thepurpose of this disclosure, a process control module may be any part orportion of a process control system including, for example, a routine, ablock or any element thereof, stored on any computer readable medium.Control routines, which may be modules or any part of a controlprocedure such as a subroutine, parts of a subroutine (such as lines ofcode), etc., may be implemented in any desired software format, such asusing object oriented programming, using ladder logic, sequentialfunction charts, function block diagrams, or using any other softwareprogramming language or design paradigm. Likewise, the control routinesmay be hard-coded into, for example, one or more EPROMs, EEPROMs,application specific integrated circuits (ASICs), or any other hardwareor firmware elements. Still further, the control routines may bedesigned using any design tools, including graphical design tools or anyother type of software/hardware/firmware programming or design tools.Thus, the controller 11 may be configured to implement a controlstrategy or control routine in any desired manner.

In some embodiments, the controller 11 implements a control strategyusing what are commonly referred to as function blocks, wherein eachfunction block is an object or other part (e.g., a subroutine) of anoverall control routine and operates in conjunction with other functionblocks (via communications called links) to implement process controlloops within the process control system 10. Function blocks typicallyperform one of an input function, such as that associated with atransmitter, a sensor or other process parameter measurement device, acontrol function, such as that associated with a control routine thatperforms PID, fuzzy logic, etc. control, or an output function whichcontrols the operation of some device, such as a valve, to perform somephysical function within the process control system 10. Of course,hybrid and other types of function blocks exist. Function blocks may bestored in and executed by the controller 11, which is typically the casewhen these function blocks are used for, or are associated with standard4-20 ma devices and some types of smart field devices such as HARTdevices, or may be stored in and implemented by the field devicesthemselves, which can be the case with Fieldbus devices. While thedescription of the control system is provided herein using a functionblock control strategy, the disclosed techniques and system may also beimplemented or designed using other conventions, such as ladder logic,sequential function charts, etc. or using any other desired programminglanguage or paradigm.

As illustrated by the exploded block 30 of FIG. 1, the controller 11 mayinclude a number of single-loop control routines, illustrated asroutines 32 and 34, and, if desired, may implement one or more advancedcontrol loops, illustrated as control loop 36. Each such loop istypically referred to as a control module. The single-loop controlroutines 32 and 34 are illustrated as performing single loop controlusing a single-input/single-output fuzzy logic control block and asingle-input/single-output PIE) control block, respectively, connectedto appropriate analog input (AI) and analog output (AO) function blocks,which may be associated with process control devices such as valves,with measurement devices such as temperature and pressure transmitters,or with any other device within the process control system 10. Theadvanced control loop 36 is illustrated as including an advanced controlblock 38 having inputs communicatively connected to one or more AIfunction blocks and outputs communicatively connected to one or more AOfunction blocks, although the inputs and outputs of the advanced controlblock 38 may be connected to any other desired function blocks orcontrol elements to receive other types of inputs and to provide othertypes of control outputs. The advanced control block 38 may be any typeof model predictive control (MPC) block, neural network modeling orcontrol block, a multi-variable fuzzy logic control block, areal-time-optimizer block, etc. It will be understood that the functionblocks illustrated in FIG. 1, including the advanced control block 38,can be executed by the controller 11 or, alternatively, can be locatedin and executed by any other processing device, such as one of theworkstations 13 or even one of the field devices 19-22.

With reference now to FIG. 2, the controller 11 may have any number ofcontrol modules 50, 52, and 54 that define and implement correspondingprocess control routines to control the on-line process. Thus, thecontrol modules 50, 52 and 54 may be implemented in connection with anoperational environment or mode controlled by a module 56 and generallyassociated with normal, scheduled control of the process. As describedabove, each control module 50, 52 and 54 may have any number of functionblocks, including control function blocks.

In accordance with some embodiments of the disclosed technique,parameter values and other operating condition data are passed from thecontrol modules 50, 52 and 54 to a data collection function 58 of amodel identification routine or module 60. Generally speaking, theparameter values and other operating condition data are made available(or otherwise communicated) during execution of the control modules 50,52 and 54 and function blocks thereof. Because such execution is rathercontinuous during the scheduled process control activities, thecommunication of the parameter values and other operating condition datamay also be continuous.

Like the function blocks, the data collection function 58 may, but neednot, be implemented in object-oriented fashion as an object(s) (orobject entity). Regardless of its structure, the data collectionfunction 58 may include one or more routines defining the procedures tobe implemented in the data collection, including any data handlingprocedures. The routines of the data collection function 58 may thuscoordinate, support or implement the storage of the collected data in,for instance, one or more registers 62 or other memories. The proceduresexecuted by the data collection function 58 may include determining whento collect the data from the control modules 50, 52 and 54, as describedbelow.

More generally, the data collection function 58 may include one or moreroutines to support the automatic collection, gathering, receipt orother handling of the parameters and other operating condition data. Tothe extent that the automatic collection or other handling of theparameters and data is implemented by the data collection function 58,less computational requirements are placed on the module 56, the controlmodules 50, 52 and 54, and any control blocks thereof. As a result ofsuch separation of the model identification procedure from the controlfunction blocks, the function block memory and execution requirementswill be the same whether model identification is enabled or disabled.Furthermore, the number of parameters and associated memory requirementsadded to the control blocks to support adaptation (i.e., adaptivecontrol) is minimized.

The separation of the modules 56 and 60 also allows some embodiments toprovide an option to disable the model identification module 60 and,thus, the data collection function 58. Disabling model identificationmay be useful if, for instance, it is determined that the controller 11has insufficient memory or time for the calculations and otherprocessing. On a related note, the use of the identified models toprovide adaptive control may be also be enabled or disabled on a loop,area, system or controller basis.

Separate model identification functionality also supports thecoordination of process input changes. Such coordination is madepossible because model identification within the controller iscentralized in one process. For example, when no set point changes arebeing made, the model identification module 60 (or other element orroutine) may automatically inject changes in the controller output.These changes may be coordinated in a manner to minimize the impact onprocess operation. These changes may thus be distributed over time.

Separate model identification also means that the processing of data formodel identification may be performed in free or down time for thecontroller 11, or at any other time deemed suitable by the controller11. As a result, the implementation of model identification processingavoids adversely impacting scheduled control functionality provided by,for instance, the module 56. As a result, in some embodiments, the modelidentification module 60 may be implemented by the controller 11 in thebackground, while the process is on-line, and at strategicallyadvantageous times during the scheduled control and other activitiesundertaken by other modules or components of the controller 11.

In alternative embodiments, the model identification functionality maybe integrated into the control function blocks themselves.

In some embodiments, the parameter and other data is passed from thecontrol modules 50, 52 and 54 to the data collection function 58automatically whenever a control block executes. In this sense, the datacollection module 58 may be implemented continuously to support the datacollection procedure at any time during operation of the process. Duringthose times when control is not scheduled to execute, the datacollection function 58 may then examine the collected data to determineif a process model should be generated (e.g., created or identified). Inalternative embodiments, the controller 11 may examine or otherwiseprocess the collected data periodically or in some other scheduledmanner. Of course, in still other alternative embodiments, the datacollection function 58 may not be implemented by, or as part of, thecontroller 11 to, for instance, minimize computational demands, or forany other desired reason. Further details regarding instances where suchprocessing may not be embedded in the controller 11 are set forth belowin connection with embodiments in which the disclosed technique islayered onto (or otherwise integrated with) a pre-existing processcontrol system.

The data collected by the data collection function 58 may generallyinclude values for the process inputs and outputs or the operating setpoint for a particular control loop implemented by the controller 11(or, more generally, the process control system 10). For each of theseparameters, values are collected and stored over a time period beginningbefore a trigger event and lasting until steady state is reached. Insome cases, the trigger event may involve the detection by, forinstance, the data collection function 58 of a change in the processinput or set point.

In some cases, what constitutes a trigger event may depend on theoperational mode of the control loop. When a control loop resides in an“automatic” mode of operation, the loop is continuously adjusting thecontroller output (i.e., the manipulated process input) to maintain aprocess output (i.e., the controlled parameter of the loop) at anoperator-specified set point. Thus, in automatic mode, a change in theset point will constitute a trigger to analyze the change in processinputs and outputs and, thus, to develop a model. If the operator never(or rarely) changes the set point and the loop remains in automaticmode, then a small change may be injected in the controller output sothat there is a trigger to create a model.

When the loop resides in a “manual” mode, then the controller output isset by the operator, i.e. the control algorithm is not adjusting theoutput. Thus, in manual mode, a change in the output introduced by theoperator constitutes a trigger for analyzing process inputs and outputto obtain a model.

The three above-described trigger events may be used for the developmentof feedback models. For feedforward model identification, the triggerevent may be a change in the feedforward input value.

Once the trigger event is detected, the modules 56 and 58 communicate inany desired fashion to support the data collection. In some embodiments,the data collection is facilitated by the module 56, which may alsoindicate the detection of a trigger event. More specifically, thecontrol loops implemented by the control modules 50, 52 and 54 maycontinuously provide access to the data or otherwise make the dataavailable. As a result, data collected for some time before the triggerevent may also be analyzed to determine the process model. For example,a PID control loop for which data is collected may provide access to thecurrent data values for the process variable used in the block execution(e.g., PV), the block output value (e.g., OUT), the feedforward controlinput value (e.g., FF_VAL), the set point, and any one or moreparameters that indicate the loop mode of operation. In some cases, thedata collection function 58 may facilitate the selection of theparameter or other data values. Alternatively or in addition, the modelidentification module 60 may include a configuration list block(s) 64that determines which parameters need to be collected. To that end, theconfiguration list block 64 may include a memory or other storagemechanism for the list data. Stored along with the identified parametersmay be a list or other identification of the control blocks or modulesfor which the models are to be generated.

At some point following the data collection associated with a triggerevent, the model identification module 60 may implement a modelidentification algorithm or calculation routine 66. The modelcalculation routine 66 may also analyze the calculated models inaddition to merely performing the calculations. Such analysis mayinvolve process and/or control diagnostics to determine, among otherthings, the quality of the model. The calculated models may then bepassed along to a storage or other block 68 that holds the lastidentified model(s) for each control loop. In some cases, a control loopmay have two models stored to support, for instance, both feedback andfeedforward control. As shown in FIG. 2, the calculated models arepassed to the block 68 after and depending on the quality of the modelas determined by the model diagnostics of the routine 66.

The quality of the model may also be determinative of whether the modelis passed along to the control function blocks of the control modules50, 52 and 54. In the exemplary embodiment of FIG. 2, each of thecontrol modules 50, 52 and 54 incorporates at least one control loophaving adaptive control and, accordingly, receives process models fromthe model identification routine 60 as shown. However, the modelscalculated and otherwise identified by the disclosed technique may beprocessed and provided based on the aforementioned model qualitydetermined by the block 66 and, in some cases, on the operational stateof the control function block receiving the new model.

With reference now to FIG. 3, a user of one of the workstations 13 mayinitiate the creation of a process model by selecting real-time orhistorical data provided via a tuning or other application 70implemented on the workstation 13. Such user-initiated process modelcreation may be in addition to the processing described in connectionwith FIG. 2. In fact, in the exemplary embodiment shown in FIG. 3, thecontroller 11 to which the model created by the tuning application 70 ispassed also includes the model identification routine 60 and itsconstituent parts, i.e., the data collection function 58, the modelcalculation routine 66, etc.

Apart from the source of the parameter values and other operatingcondition data used to create the process model, the workstation 13 mayimplement the same or similar steps toward creation of the processmodel. For instance, the workstation 13 may include a model calculationand diagnostics module or block 72 similar to the block 66 of thecontroller 11. The model calculation block 72 may accordingly determinethe quality and other aspects of the created block prior to, or inconnection with, passing the block to the controller 11 and the storageblock 68, as shown.

In some embodiments, the workstation 13 may have additional oralternative applications that provide similar functionality. In onecase, the other application may provide one or more display interfacesthat support the analysis and/or inspection of the process modelsidentified via the disclosed techniques. Further information regardingthis application is set forth herein below. In connection with thegeneration of the additional process models, however, these workstationapplications may generate a trend window or display interface thatprovides an opportunity to select process data for use in the modelcreation. Using these trend windows or other interfaces, a user mayselect the data, including the time window. In these cases, the time tosteady state may accordingly be determined via the time window selectedby the user. Alternative embodiments may provide other mechanisms formanually or automatically selecting the time window.

Practice of the disclosed technique is not limited to a modelidentification routine located in either the controller 11 or theworkstation 13 of the process control system 10. More generally, themodel identification procedures described herein may be implemented inother devices or systems, either individually or in distributed fashion,and in varying degrees of cooperation and/or communication with thecontrol loops from which the underlying parameters or data is collected.For instance, in some cases, the model identification procedures may beimplemented in a remote manner, and/or by a system layered onto aprocess control system via an OPC or other interface.

As described above, practice of the disclosed technique is not limitedto systems implementing adaptive control routines. However, theidentification of process models via the disclosed techniques may beutilized to support such routines, when desired.

As shown in FIG. 4, an adaptive control function block 74 for use inconnection with the disclosed technique may include one or memories orother storage mechanisms 76 to save or store a predetermined number(e.g., five) of process models that have been identified as describedabove. In operation, one of the process models stored in the memory 76may then be selected for use via a logic block 78 responsive to one ormore parameters. In the exemplary embodiment of FIG. 4, the block 78selects the process model based on a selected or otherwise determinedprocess state parameter provided via an input 80. Two other parameters82 and 84 may also be relied upon for the determination, and maycorrespond with feedback and/or feedforward rules or a setting thatallows the operational state to adapt to changing conditions.

The process models for the function block 74 may, but need not, beassociated with operational regions (e.g., Region 1, Region 2, etc., asshown). The process models may also be identified in pairs in accordancewith the control scheme of the function block. In this exemplary case,each region is determinative of a pair of process models in support ofboth feedback and feedforward processing. Upon selection of the region,the pair of feedback and feedforward models may be utilized by the block78 to calculate feedback and feedforward tuning parameters,respectively. In the exemplary case shown in FIG. 4, the feedforwardtuning parameters are provided to a dynamic compensation block 88 alsoresponsive to a feedforward control input value (e.g., FF_VAL) for,e.g., dead time and lead/lag dynamic compensation. The results of thedynamic compensation, along with the feedback tuning parameters, may bepassed to a block or routine 88 responsible for the implementation ofthe control algorithms for the function block. In this case, thefeedback and feedforward parameters modify PID and fuzzy logicalgorithms, but any control schemes, or control scheme combinations, maybe utilized.

The function block 74 also includes a block or routine 90 to supporton-demand modifications of the control loop tuning. To this end, theblock 90 may be responsive to a user command entered via the controller11, the workstation 13 or any other element of, or device incommunication with, the process control system 10. In general, the modelthat has been automatically identified for the loop may, on demand, beused with a selected tuning rule to set the loop tuning. If a model hasnot previously been identified, then a user command may initiate a relayoscillation or other technique to inject changes in the controlleroutput. The resulting process-model developed from the process responseto the change in controller output may then be used with a selectedtuning rule to set the loop tuning or to provide tuning recommendations.

In some cases, the process models generated via the block 90 or as aresult of a triggering event (e.g., a set point or other parameter valuechange) may first be held for viewing before a download to thecontroller 11 or function block 74. For example, such models may beclassified as “unapproved models” until analysis via a user interfacehas provided approval for implementation. In some embodiments, suchapproval may alternatively or additionally be provided automatically viadiagnostic or other functionality in the controller 11 or workstation13.

FIG. 5 shows an adaptive block framework in the context of an adaptiveMPC control block 92 in which a number of different operational regionsare also supported. In this context, a plurality of process modelsidentified via the model identification routine 60 may still be passedto a memory or storage 94 (similar to the memory 76 of FIG. 4) as shown,but the model parameters may be processed by an MPC controllergeneration routine 96 prior to implementation in the function block 92.More specifically, the routine 96 may generate a corresponding MPCcontroller for storage in a memory 98 based on the identified models. Alogic block 100 may then select or switch between the models that areused to generate the MPC controller based on changes in a stateparameter and other parameters provided via inputs or memories 102, 104and 106, as shown.

The MPC controller associated with the selected process model may thenbe provided to an MPC controller block 108 for implementation in theon-line process. The MPC controller block 108 may support automatedon-demand testing of the selected MPC controller, which may be initiatedby the introduction of a disturbance input 110 or otherwise, as desired.

In some cases, the exemplary adaptive control function blocks shown inFIGS. 4 and 5 (as well as other blocks for use with the disclosedtechnique) generally support three modes of operation: a learn mode, aschedule mode and an adaptive mode. In the learn mode, process modelsmay be collected but are not automatically used to determine the looptuning. In the schedule mode, new process models may be collected andthose models that are approved will be automatically used to determineloop tuning parameters. In the case of an adaptive MPC block, suchapproved and applied models will then be used in control generation inaccordance with the current operating region; as the controllers will beautomatically switching with the current operating region. In theadaptive mode, process models are collected, automatically approved andthen automatically used to determine loop tuning parameters. While thedefault setting for each function block may be the learn mode, thedisplay interfaces provided via, for instance, one of the applicationsimplemented on the workstations 13 may provide an opportunity to changethe setting, as desired.

With reference now to FIG. 6, one or more applications implemented bythe workstations 13 provide performance monitoring, analysis, managementand related functionality for the control loops and process modelsidentified via the disclosed techniques. For example, the performancemonitoring functions may include the generation of a process modelhistory in which data indicative of the identified process models isentered for subsequent use or analysis. Further details regarding thegeneration and use of a process model history are set forth below. Atone level, the history data may specify the process model parameters(e.g., dead time, time constant and gain) that completely define eachprocess model identified by the disclosed techniques. Armed with thathistorical data, a number of analyses may be conducted regarding thecontrol loop, its tuning, the control scheme (e.g., adaptive ornon-adaptive), etc.

In some embodiments, one aspect of the process model history is directedto the generation of an event chronicle for the identified processmodels. More specifically, whenever a process model is identified eitherautomatically in the controller 11 (FIG. 2) or on-demand from real-timeor historical data (FIG. 3), the model identification routine 60 maysend an alert (or other message) to an event chronicle or trackingmodule 112. The event chronicle module 112 responds to the alert bygenerating data specifying the time and date of the modelidentification, along with any other data to facilitate the associationof the model with the particular control loop, device, plant region,etc. In the exemplary embodiment shown in FIG. 6, data stored for eachevent includes a tag name for the device associated with the node orcontrol loop, a date/time stamp, a model type (e.g., by identifyingparameters such as dead time, time constant and gain), a control looptype (e.g., function block), a plant region number, a tuning rule, and adiagnosis indication for the control performance. The foregoing (orother) data may be stored as part of the process model history in adatabase 114 after processing by an application 116 that may, forinstance, add one or more elements to the data set. The application 116may correspond with one or more routines directed to monitoring and/ormanaging the tuning of each control loop.

The database 114 may store such historical data for control loops thatreside in multiple controllers 11 within the system 10 and need not belimited to use with any one particular type of controller. For instance,the database 114 may store such data for third-party controllers.

More generally, and as shown in the exemplary embodiment of FIG. 7,implementation of the disclosed system, method and techniques may beapplied to legacy or third-party process control systems. In otherwords, the disclosed systems and techniques may be implemented “on topof” the legacy or other process control systems.

In these cases (and other alternative embodiments), the workstation 13generally includes the above-described model identificationfunctionality otherwise implemented in the controller 11. For example,the workstation 13 may include a model identification module 118 havinga data collection function 120, a configuration list module 122, a modelcalculation routine 124, and a memory 126 for storing the lastidentified model(s) for each control loop. In addition to those elementsthat correspond with the elements of the model identification module 60of the above-described controller 11, the workstation 13 may alsomaintain a virtual controller 128 for the control system for which theprocess models are being identified. The virtual controller 128 mayinclude and store, for instance, modules reflecting the currentconfiguration of each control loop along with an identification of therespective parameters thereof. That is, the model and diagnosticinformation generated via the disclosed techniques are saved in a moduleautomatically created for that node. In this way, the virtual controller128 may be utilized to present information via tuning, diagnostics, etc.in exactly the same manner as would be done in connection with loopsimplemented in the controller 11. In the event that the namingconventions of the control system differ from those of the workstation13, definitions correlating the parameters may be made via the interfaceconfiguration block 134 or other element of the workstation 13.

To support the broad application of the disclosed techniques, theworkstation 13 may include an OPC (Open Process Control) or other clientinterface 132 configured via a block 134 to access loop dynamicparameters. Generally speaking, the communication link between theworkstation 13 and the legacy or third-party control system may beestablished by identifying an OPC server 136 thereof and, in some cases,other communication settings, such as an identification of one or morecontroller(s) 138 involved in the model identification process. To avoidopening many (e.g., unnecessary) communication ports, such OPCconnections may be made using tunneler software.

Further details regarding the applications provided via the workstation13 (in either a legacy or standard, integrated context) to control andmanage implementation of the disclosed technique are now provided. Theapplications generally support the identification of process models, asdescribed above, and also provide the functionality associated with theuse of the identified models. As described above, the process modelsneed not be generated merely for use in connection with an adaptivecontrol scheme. The identification of process models in accordance withthe disclosed technique is implemented regardless of whether the controlroutine is an adaptive control routine. Identifying process models forall of the control loops—both adaptive and non-adaptive—generallyprovides the capability to perform a number of different analyses of theprocess, the process control system, and specific elements thereof. Thatsaid, in some cases, the disclosed system may provide an option via adialog box, window, faceplate, or other display interface to disablemodel identification on a node-by-node (or loop-by-loop) basis. Thedisplay interface may be one of a number of display interfaces generatedvia the implementation of the applications running on the workstations13. Examples of such display interfaces are provided in FIGS. 9-16.

Referring again to FIG. 1, as a general matter, the workstations 13include (either individually, distributed or any other fashion) a suiteof operator interface applications and other data structures 140 whichmay be accessed by any authorized user (e.g., a configuration engineer,operator, etc.) to view and provide functionality with respect todevices, units, etc. connected within the process plant 10. The suite ofoperator interface applications 140 is stored in a memory 142 of theworkstation 13 and each of the applications or entities within the suiteof applications 140 is adapted to be executed on a respectiveprocessor(s) 144 associated with each workstation 13. While the entiresuite of applications 140 is illustrated as being stored in theworkstation 13, some of these applications or other entities may bestored and executed in other workstations or computer devices within orassociated or in communication with the system 10. Furthermore, thesuite of applications 140 may provide display outputs to a displayscreen 146 associated with the workstation 13 or any other desireddisplay screen or display device, including hand-held devices, laptops,other workstations, printers, etc. Likewise, the applications within thesuite of applications 140 may be broken up and executed on two or morecomputers or machines and may be configured to operate in conjunctionwith one another.

FIG. 8 shows an exemplary workstation 13 in greater detail in connectionwith the implementation of the disclosed system, method and modelidentification techniques. Specifically, the suite of applications 140may include a number of applications, routines, modules, and otherprocedural elements directed to the implementation of model-basedmonitoring and management of the control system 10, as described herein.The applications, routines, modules and elements may be implemented viaany combination of software, firmware and hardware and are not limitedto the exemplary arrangement shown in FIG. 8. For instance, one or moreapplications may be integrated to any desired extent.

The application suite may include a historian application 148 dedicatedto supporting the recordation of process model data (e.g., parameters)as the models are identified via the above-described techniques. To thisend, the historian application 148 may communicate with the historiandatabase 12 or any other memory or storage mechanism. As describedabove, the process model data may be stored in connection or associationwith data chronicling the identification of the process model (or thecollection of the data leading thereto). The historian application 148may also provide analytical functionality such as the calculation oftotals, averages and other values for selected model parameters. Thehistorian application 148 may facilitate the viewing of such calculatedvalues, as well as the underlying stored data, via one or more displayinterfaces.

A third-party interface application 150 may be provided to support andmaintain a communication link with a third-party or legacy processcontrol system, as described in connection with FIG. 7. To that end, theapplication 150 may generate a number of display interfaces tofacilitate the configuration of the communication link, maintain andutilize the virtual controller 128, and otherwise support the interface.

Further display interfaces may be provided by an application 152directed to supporting communications with the controller 11. Suchcommunications may involve or include the configuration and maintenanceof adaptive control routines executing in the controller 11. As is thecase throughout the application suite, the display interfaces may takeany form, including without limitation dynamos, faceplates, detaileddisplays, dialog boxes, and windows, and may be configured for displayon different display types.

The application suite may include an application 154 dedicated to use ofthe process model information in connection with tuning. As a result ofthe above-described model identification techniques, the tuningapplication 154 is directed to improving process control performance bycalculating tuning parameters automatically from normal day-to-daychanges in the plant, or from on-demand tuning tests. The tuning resultsmay be used for both “open-loop” tuning recommendations, and for“closed-loop” adaptive control.

More specifically, the tuning application 154 may generate a number ofdisplay interfaces to support the performance of continuous tuningcalculations for all control loops in either open loop or closed loopoperation. The tuning calculations support both standard and adaptivecontrol, on PID, fuzzy logic, and MPC controllers and, thus, providetuning recommendations for both feedback and feedforward control. Thetuning application 154 may also provide on-demand tuning, as describedabove, using either a relay oscillation or other procedure.

The tuning application 154 has access to the process model history datastored in the historian database 12 (or elsewhere, as desired) and,thus, may calculate optimal tuning using historical process model data.To that end, the display interfaces may provide or include tools toeasily peruse the history to locate and select data suitable for suchtuning calculations. This aspect of the display interface(s) generatedby the tuning application 154 generally allows a user to change modelparameters (e.g., time to steady state, event trigger threshold) andre-identify models, or identify models for loops that were notpreviously enabled for automatic model identification.

The tuning application may also provide an interface to support analysisof a history of tuning calculation results. This capability mayfacilitate the analysis of adaptive control opportunities and theimprovement of adaptive control configurations.

As described above, the tuning application 154 may provide an interfaceto support the introduction of control “perturbations” that helpidentify controller tuning when there are few manual changes to theprocess (i.e., automatic injection on controller output). An option maybe provided via the interface to disable perturbations once good tuningis calculated. If multiple control loops are being perturbed, the movesmay be synchronized to distribute and minimize the process disturbance.

The tuning application 154 may be responsive to process states and otherstatus indications, such that any calculation results are identifiedaccordingly. In this way, the disclosed system avoids the use ofinformation calculated in the wrong state or with bad process data. Tothat end, model-related calculations may indicate whether the resultsare good, bad or not available, with explanations where appropriate.

The tuning application 154 may also generate summary reports to convey,among other things, tuning recommendation information and a user logthat documents tuning changes and any adaptive control tuning analysis.

Further details regarding the display interfaces generated by the tuningapplication 154 (either alone or in conjunction with other applications)are presented in connection with FIGS. 12-16, which generally depict theviews of the process models and control loops provided to a user tofacilitate the above-described functionality.

With continued reference to FIG. 8, an application 156 is generallydirected to automatic control performance monitoring utilizing theprocess models identified via the disclosed techniques. The application156 is more specifically directed to improving process controlperformance by facilitating or automatically implementing (i) theidentification of opportunities for control improvement, (ii) theanalysis and diagnosis of the source of control problems, and (iii) thegeneration of meaningful performance reports for operations, control andmaintenance personnel. To this end, the application 156 may generate acontrol performance index based on the process models. This“model-based” index provides a better benchmark to identify controlloops that need re-tuning. The new index measures the opportunity forimproving control based on factors such as process variability, theidentified process model, and existing controller tuning. Suchperformance monitoring may, if applicable, take into consideration unitstates and exclude performance calculations when the loop is in aninappropriate unit state, or when other status indications (e.g.,Fieldbus status) or I/O communications are bad. Valve stiction, backlashand other valve diagnostic indices may also be provided for all valves.

The foregoing features and those described below are generally providedvia a comparison of control performance done by utilizing the processmodels that are automatically created via the disclosed techniques.Through the use of the process models, poorly tuned control loops andchanges in the process that impact control performance may beidentified. Deviations in the process model from the historic values maybe used to flag the control loop as a potential process problem.

Again, using the process models, an oscillation index may also begenerated by the application 156 to identify loops that are oscillating.More specifically, an oscillation analysis tool may identify other loopsthat have the same oscillation period and may be interacting with theprimary loop. This information may then be used to identify processinteractions and possible design recommendations.

Diagnostic information provided by the application 156 may beaccompanied by an indication of the expected cause of poor controlperformance. For example, diagnostics may indicate whether poor controlperformance is caused by instrumentation errors, valve stiction orbacklash, process interactions, or controller tuning.

Generally speaking, the control performance monitoring information maybe provided in any desired form, including a number of customizeddisplay interfaces and reports. Historical performance reporting may beprovided to display how a control loop has performed over auser-specified period of time. Default time periods for such reportinginclude last hour, last shift (8 hours), last day, last week, lastmonth. The user may be provided an option to “drill down” from summaryreports to access detailed loop information. The reports or interfacesmay be customized for management summaries with, for instance, anoverall weighted performance index for plant-wide and individual processunits, trends and/or tables comparing the current period with priorperiods, and lists of top priority loops with a correspondingperformance measure. Maintenance reports may present control loopperformance indices and prioritize work items based on their-relevantimportance to plant operations. Other reports may provide statisticsincluding data for the control performance index, standard deviation,oscillation index, process model (if available), auto and crosscorrelation, histogram, power spectrum, etc.

Further details regarding the information provided by the application156 are provided via the exemplary display interfaces depicted in FIGS.9-12.

The application suite may also include a separate control loop analysisapplication 158. In some embodiments, the application 158 is madeavailable via the display interface(s) generated by the application 156.In any event, the application 158 supports analysis 6f historian orreal-time data collected in connection with the above-described modelidentification techniques. The data may be presented via an interfacethat facilitates the examination of variation in control from unmeasureddisturbances and measurement noise. For example, the problems identifiedvia the applications 154 and 156 may be further examined using theanalysis application 158 for diagnosis. To that end, the displayinterface generated thereby may provide options for calculating powerspectrum, autocorrelation and histogram data.

An advisor application 160 may generally provide functionality thatutilizes the identified models in connection with diagnostics to detectabnormal conditions or opportunities to improve the control schemethrough tuning or algorithm modifications. The information provided bythe advisor application 160 may be provided in any type of displayinterface, including a faceplate generated via the workstation 13, thecontroller 11 or any other element in communication with the system 10.In one specific example, the display interface may have a flag forindicating the display of a new advisory message, such as “CheckTuning.”

More generally, the advisor application 160 may provide recommendationsgenerated as a result of analysis or diagnostics performed by any one ofthe applications in the suite. Furthermore, the recommendations need notbe provided by a display interface generated by the advisor application,but rather may be sent for display to any one or more of theapplications in the suite. Thus, recommendations and messages such as“New Tuning Available,” “Examine Process—significant change in processhas been detected,” “Check Valve—dead band/hysteresis large,” “CheckTuning—loop unstable,” and “Control could be improved using MPC/Adapt”may be generally provided via the workstations 13 or other devices incommunication with the process control system 10. In addition to thedisplay of the message or recommendation, details regarding theunderlying condition may be stored as a history or other parameter forthe control loop. Subsequent access or use of the data stored for thecontrol loop may then cause the details or associated message to bedisplayed for a user of the advisory or other application in the suite.

Other applications that also support the implementation of the disclosedtechniques include a control studio application 162 to facilitatenavigation within the process control system 10 and a report generationapplication 164 for the generation of the aforementioned reports.Lastly, one or more memories or databases 166 may also be provided aspart of the application suite.

FIG. 9 depicts an exemplary display interface 168 that may be generatedby the performance monitoring application 156 (or, alternatively, anyone or more of the other applications) to present overview informationresulting from the process model inspection analysis. In this specificexample, the display interface 168 presents information indicative ofthe condition of the control routines or modules in the entire processcontrol system 10, or any area thereof selected via a hierarchy-treepanel 170. The control performance may be specified and summarizes in achart panel 172 via categories, including “Incorrect Mode,” “LimitedControl,” Uncertain Input,” and “Large Variability.” The assignment orclassification of a control module, function block or routine into oneof these categories is generally enabled by, and may be automaticallyimplemented using, the process models identified via the disclosedtechniques. The display interface 168 also includes an asset alert chartpanel 174 to present statistical information on the numbers of assetsdeemed to be failed, requiring maintenance soon, having an advisoryalert, or experiencing a communication failure.

FIG. 10 depicts an exemplary display interface 176 that may also begenerated by the performance monitoring application 156. The displayinterface 176 also generally presents control performance information,but on a more detailed level. In this example, performance informationis presented for each control loop or module in an area selected in thehierarchy-tree panel. Each abnormal condition detected for a particularcontrol loop may be noted in a table distinguishing between problemsassociated with an abnormal mode, limited control, input status, highvariability or an inactive, related device. A priority level may also bedisplayed, along with an indication as to whether a report has beengenerated describing the abnormal condition.

FIG. 11 depicts an exemplary display interface 178 that may also begenerated by the performance monitoring application 156. The displayinterface 178 is similar to the interface 176 of FIG. 10, and differs inthe control level at which the performance information is presented. Inthis case, a module or loop is selected via the panel 170, and theperformance information is presented for each function block thereof.Diagnostic information for a particular block may then be accessed byselecting (e.g., right-clicking) on the block name displayed in thetable.

FIG. 12 depicts an exemplary display interface 180 that may be generatedby one or more of the applications, including the tuning application 154and the performance monitoring application 156. Generally speaking, thedisplay interface 180 facilitates the examination of results ofdiagnostic calculations for a selected control element (e.g., PID1).Limit values for the statistics derived via the calculations are alsodisplayed for comparison and user-modification, as desired. When a limitis exceeded, an alarm may indicate the associated condition. Moregenerally, the information presented in the display interface 180 andthe underlying calculations are indicative of how the stability of thecontrol loop is continuously monitored as a result of the process modelidentification techniques disclosed herein.

FIG. 13 depicts an exemplary display interface 182 that facilitates thesetup of a control loop for automatic process model identification aswell as on-demand model identification. A number of panels are providedvia the interface 182 to specify trigger event types, trigger eventlevels, parameter change maximums, etc. In this way, the displayinterface 182 enables a user to customize the process modelidentification procedure on a node-by-node, or loop-by-loop basis.

FIG. 14 generally depicts the way in which a user may visualize thesaved process models to, among other things, determine how many regionsare required. More specifically, a display interface 184 includes apanel 186 listing process model history information and a model graphpanel 188 that shows, via respective horizontal lines, the approvedmodel values and, via the dots, the parameters of process modelsidentified and stored in the history database. As described above,respective models may be approved for a number of regions (e.g., five),and the variance of the model parameters may facilitate theidentification of the regions and otherwise help with tuningrecommendations.

FIGS. 15 and 16 depict process model information for a recentlyidentified model in connection with a fuzzy logic control block and anMPC block, respectively. To that end, display interfaces 190 and 192provide respective graphical representations of the process model, alongwith a number of panels 192, 194, 196 and 198 to support testing, tuningcalculations, controller parameter settings, tuning simulation, andtuning selection.

The terms “identifying,” “identification” and any derivatives thereofare used herein in a broad sense in connection with the use of processmodels to include the creation of, generation of, and other processingto arrive at, either an entire process model, any one or more parametersto define it, or any other defining characteristics thereof.

Any of the above-described applications may be implemented as routines,modules or other components of one or more integrated applications. Thedisclosed arrangement of application functionality is provided merelyfor ease in illustration and is not indicative of the broad range ofmanners in which the functionality may be provided to an operator orother user. Furthermore, the above-described applications may beprovided in varying form depending on user profile, context, and otherparameters, as desired. For example, the display interface viewsgenerated for one user type (e.g., engineering) may differ in contentand other ways from the views generated for a different user type (e.g.,maintenance).

When implemented, any of the software described herein may be stored inany computer readable memory such as on a magnetic disk, a laser disk,or other storage medium, in a RAM or ROM of a computer or processor,etc. Likewise, this software may be delivered to a user, a process plantor an operator workstation using any known or desired delivery methodincluding, for example, on a computer readable disk or othertransportable computer storage mechanism or over a communication channelsuch as a telephone line, the Internet, the World Wide Web, any otherlocal area network or wide area network, etc. (which delivery is viewedas being the same as or interchangeable with providing such software viaa transportable storage medium). Furthermore, this software may beprovided directly without modulation or encryption or may be modulatedand/or encrypted using any suitable modulation carrier wave and/orencryption technique before being transmitted over a communicationchannel.

While the present invention has been described with reference tospecific examples, which are intended to be illustrative only and not tobe limiting of the invention, it may be apparent to those of ordinaryskill in the art that changes, additions or deletions may be made to thedisclosed embodiments without departing from the spirit and scope of theinvention.

1. A method of controlling a process control system having a pluralityof control loops, the method comprising the steps of: implementing aplurality of control routines to control operation of the plurality ofcontrol loops, respectively, the plurality of control routinescomprising at least one non-adaptive control routine; collectingoperating condition data in connection with the operation of eachcontrol loop of the plurality of control loops; and, identifying arespective process model for each control loop of the plurality ofcontrol loops from the respective operating condition data collected foreach control loop of the plurality of control loops.
 2. The method ofclaim 1, further comprising the step of storing data indicative of therespective identified process models in a respective process modelhistory for each control loop of the plurality of control loops.
 3. Themethod of claim 1, further comprising the steps of: examining theoperating condition data to detect a change therein; and, triggering theprocess model identifying step when the change is detected.
 4. Themethod of claim 1, wherein the identifying step is performed in responseto a user command to calculate the process model based on the collectedoperating condition data.
 5. The method of claim 4, wherein thecollected operating condition data is indicative of a response to aninjected parameter change applied as a result of the user command. 6.The method of claim 1, wherein the operating condition data isindicative of on-line operation of a process controlled via theoperation of the plurality of control loops.
 7. The method of claim 1,further comprising the step of monitoring the respective process modelsidentified for each control loop to evaluate control loop performance.8. The method of claim 1, further comprising the step of analyzing therespective process models identified for each control loop to determinewhich control loops should utilize an adaptive control scheme.
 9. Themethod of claim 1, further comprising the step of analyzing therespective process models identified for each control loop to diagnosecontrol problems.
 10. A method of controlling a process control systemhaving a plurality of control routines, the method comprising:collecting operating condition data during implementation of theplurality of control routines; detecting an event indicative of aprocess change in connection with a control routine of the plurality ofcontrol routines associated with the process change; identifying aprocess model for the control routine associated with the processchange; and, storing data indicative of the generated process model indeveloping a process model history for the control routine associatedwith the process change.
 11. The method of claim 10, further comprisingthe step of automatically collecting data for the identifying step upondetection of the event.
 12. The method of claim 10, further comprisingthe step of identifying respective process models for each controlroutine of the plurality of control routines.
 13. The method of claim12, wherein the plurality of control routines comprises a controlroutine that implements a non-adaptive control scheme.
 14. The method ofclaim 12, further comprising the step of monitoring the respectiveprocess models identified for each control routine to evaluate controlroutine performance.
 15. The method of claim 12, further comprising thestep of analyzing the respective process models identified for eachcontrol routine to determine which control routines should utilize anadaptive control scheme.
 16. The method of claim 12, further comprisingthe step of analyzing the respective process models identified for eachcontrol routine to diagnose control problems.